Structures to represent poorly formed HTML documents

ABSTRACT

Disclosed is a method of restructuring an input HTML document to comply with strict HTML. An input HTML document is linearly traversed to create a hierarchical tree structure representation (FIGS.  2 A- 2 F), the traversal maintaining a current insertion point ( 206, 210 ) for elements within the tree structure representation. During the traversal, elements ( 208 ) of the input HTML document that violate strict HTML are identified Each element is then processed individually, initially by retracing the tree structure representation from the current insertion point to identify an further insertion point from which the identified element can depend, the retracing comprising noting each parent element of the identified element passed during said retracing. Then, at the further insertion point, new elements ( 218 ) are created in the tree structure representation to correspond to those parent elements passed during the retracing, the new elements being created in reverse chronological order to that encountered during the retracing. The identified element ( 208 ) is then append to a terminal one of the new elements. The tree structure representation can then be converted into an output HTML document.

COPYRIGHT NOTICE

[0001] This patent specification contains material that is subject to copyright protection. The copyright owner has no objection to the reproduction of this patent specification or related materials from associated patent office files for the purposes of review, but otherwise reserves all copyright whatsoever.

TECHNICAL FIELD OF THE INVENTION

[0002] The present invention relates to structuring within electronic documents and, in particular, to structuring forms within computer languages such as mark-up languages and documents formed therefrom.

BACKGROUND

[0003] The field of computer coding covers many different coding and program schemes all of which incorporate certain rules that define the particular coding scheme and which generally must be adhered to by users of such schemes in order for results to be derived therefrom. For example, a person programming in the language Pascal must ensure their code corresponds the appropriate Pascal syntax in order for the Pascal program to operate. Where code does not comply, a “syntax error” will occur upon compilation of the program.

[0004] As opposed to programming in a highly structured language, more recently it has become common to alter or create documents using so called “mark-up languages” to provide a mechanism by which content in a document is presented in a particular environment, usually upon a display screen or printing device. One example of this is the Hypertext Mark-up Language (HTML) and another is the Extended Mark-up Language (XML). The purpose of such mark-up languages is to provide additional notation to content desired to be displayed or presented, so as to cause the content to be displayed or presented in fashion desired by the author.

[0005] The HTML document format pervades the Internet and the World Wide Web. In practice, documents structured with HTML mark-up are often in error in that they do not comply the particular internationally recognised HTML standard operating at the time of document creation. The current HTML standard at he time of drafting this patent specification may be found at http://www.w3c.org and http://www.w3c.org/TR/REC-htm140/.

[0006] The current standard for HTML documents insists that such documents be expressed as trees. Such a structure requires that each element of the document must be wholly contained by another element and, as a consequence, elements may not overlap. The experience of many indicates that it is easy to produce a document that superficially looks like HTML, but which in fact violates the tree-like hierarchical structures established by the HTML standard. Further, whilst human interpretation of such erroneous documents can often resolve ambiguities, there is often a mismatch between what makes sense according to the current standard, and that which the author of the HTML document actually intends.

[0007] Computer applications which read HTML approach such problems in a number of different ways. Some applications reject the bad HTML structure, thereby omitting the content or rendering the content in non-intuitive ways. Examples of these include “OPERA” and a number of smaller distribution Internet browsers which are preferred by some users for much more strict behaviours. Other applications try to match the user's likely intention despite of the strict errors contained in the HTML source. Examples of these include “Internet Explorer” (trade mark) manufactured by Microsoft Corporation, “Netscape Navigator” (trade mark) manufactured by Netscape Corporation, and “WebRecord” (trade mark) marketed by Canon Inc. In spite of the reasonable efforts the present inventors to determine how Internet Explorer and Netscape Navigator handle variations away from strict HTML, the present inventors have not been able to determine how those products perform in a manner so as to apparently resolve ambiguous or erroneous HTML.

[0008] A significant problem that arises from such non-compliance with the HTML standard is that there exist other languages and tools which interact with HTML documents, for example scripting language like JAVA script and styling languages like CSS2 (Cascading Style Sheet 2). Such tools expect that there is a strict tree structure in an HTML document and, as a consequence, often have no defined behaviour when interpreting a poorly formed HTML document. As a consequence an authored result cannot be guaranteed.

SUMMARY OF THE INVENTION

[0009] It is an object of the present invention to substantially overcome, or at least ameliorate, one or more disadvantages of existing arrangements.

[0010] According to a first aspect of the invention, there is provided a method of restructuring an input HTML document to comply with strict HTML, said method comprising the steps of:

[0011] (a) linearly traversing said input HTML document to create a hierarchical tree structure representation, said traversal maintaining a current insertion point for elements within said tree structure representation;

[0012] (b) during said traversal, identifying those elements of said input HTML document that violate strict HTML and, for each said identified element:

[0013] (b)(i) retracing said tree structure representation from said current insertion point to identify an further insertion point from which said identified element can depend, said retracing comprising noting each parent element of said identified element passed during said retracing;

[0014] (b)(ii) at said further insertion point, creating new elements in said tree structure representation corresponding to those said parent elements passed during said retracing, said new elements being created in reverse chronological order to that encountered during said retracing; and

[0015] (b)(iii) appending said identified element to a terminal one of said new elements; and

[0016] (c) converting said bee structure representation into an output HTML document.

[0017] According to another aspect of the invention, there is provided an apparatus for implementing the aforementioned methods. According to another aspect of the invention there is provided a computer program product including a computer readable medium having recorded thereon a computer program for implementing the method described above. Other aspects of the invention are also disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

[0018] A number of preferred embodiments of the present invention will now be described with reference to the drawings, in which:

[0019]FIG. 1 depicts the tree structure of an HTML document;

[0020]FIGS. 2A to 2F depict various processing stages for correcting poorly formed HTML;

[0021]FIG. 3 is a schematic block diagram of a general purpose computer upon which embodiments of the present invention can be practiced; and.

[0022]FIGS. 4A to 4D are flowcharts for the various preferred processing stages.

DETAILED DESCRIPTION INCLUDING BEST MODE

[0023] The principles of the preferred embodiment described herein have general applicability to computer network browsing applications. However, for case of explanation, of the preferred embodiment is described with reference to HTML and to browsers that operate on the World Wide Web (WWW) and standards applicable thereto. However, it is not intended that the present invention be limited to the described method For example, the invention may have application in other standards environments, such as error correction and data recovery for XML applications.

[0024] Prior to describing the preferred embodiment, it is appropriate to review particular standards issues addressed thereby. For instance, elements in HTML have a starting tag and an ending tag. For example, with a strict HTML syntax, a document having two paragraphs of bold text may be represented in the following fashion indicated by Code A below. Code A <BODY> <P><B>The first paragraph.</B></P> <P><B>The second paragaph.</B></P> </BODY>

[0025] Code A commences with an identifier as to the body of the particular element of code which is then followed by this first sub-tag P indicating the commencement of a paragraph. That tag is followed by a sub-tag B which effectively “switches on” a bold function for the following elements. Code A then recites the text content of the first paragraph of the document, which is concluded by a switch which turns off the bold, and a further switch which terminates the paragraph. The second paragraph is also commenced using a paragraph opening tag followed by a corresponding bold switch-on tag. The text of the second paragraph follows, then a bold switch-off tag and a paragraph terminator. The body is then terminated in an appropriate fashion.

[0026] Whilst Code A depicts strict HTML, the HTML standard permits some shortcuts or abbreviations. Code A may be abbreviated in the fashion represented below by Code B below. Code B <BODY> <P><B>The first paragraph.</B> <P><B>The second paragraph.</B> </BODY>

[0027] It will be seen from Code B that each of the paragraph terminating tags has been omitted from the code. This is permitted by HTML because, in the case of the first paragraph, this is followed by paragraph opening tag. Since HTML does not permit the nesting of paragraphs, the standard readily resolves the opening of the new paragraph as requiring that the previous paragraph has closed. The same occurs with the body terminator.

[0028] A common error in HTML drafting is to omit some of the necessary tags required by strict interpretation. An example of this is seen in Code C where the bold turn-off tag in the first paragraph and the bold tags in the second paragraph have been omitted. Such an anomaly occurs because many authors consider such syntax to mean that the bold extends into the second paragraph. Code C <BODY> <P><B>The first paragraph. <P>The second paragraph. </BODY>

[0029] The situation presented in Code C above leads to the impossible situation of one element (in this case, the bold) somehow sharing two parents. In this case, the bold element is started in the first paragraph and finished in the second paragraph This interpretation has both paragraph elements as parents to the bold element.

[0030] Because a paragraph in HTML cannot be nested inside another paragraph, the beginning of a new paragraph terminates the previous paragraph and, consequently, must terminate any elements that are children of the first paragraph.

[0031] There is another way this same type of error can occur in HTML documents, this being depicted in Code D below. Code D <BODY> <P><B>The first paragraph.<P> <P>The second paragraph. </BODY>

[0032] In the case of Code D, the closing of the first paragraph is explicit but there still exists the ambiguous termination of the bold element.

[0033] In accordance with the preferred embodiment and the above examples, the HTML syntax errors identified above are resolved by noting any elements terminated by the start of the second paragraph and by creating child nodes (ie. special node with no direct mapping to HTML) in the second paragraph that are links back to the initial elements in the first paragraph. In the case of Code D, since the closing the first paragraph is explicit, and the preferred embodiment uses the unexpected termination of the bold element as an instruction to create a link back to the next suitable containing element.

[0034]FIG. 1 illustrates the tree structure of the strict HTML of Code A discussed above. In FIG. 1, the body 102 is a root node of the expression tree forming the HTML document. The first paragraph 104 is depicted as a first child node and from which the bold switch 106 depends, followed by the text of the first paragraph 108. Similarly, the second paragraph is depicted as the second child 110 followed by its corresponding bold switch 112 and corresponding second paragraph text 114. In an HTML traversal of the tree 100, traversal commences at the root node 102 and then proceeds along a first branch to a first child 104. In order to progress to the terminal element of the first branch of the tree 100, one must pass through the bold switch 106 that operates on the text 108. In order to process the second branch, processing must reverse back along the first branch, switching off the bold 106 and terminating the first paragraph 104, before transiting the root node 102 to the second child node 110.

[0035] In the erroneous representation of Code C, the corresponding tree is incomplete in that the text 108 moves back directly to the paragraph 104 without transiting the bold 106. Under a strict HTML interpretation, and implementing limited error correction, such would provide for the second paragraph to be displayed in plain type, and not bold. In this particular example, one solution afforded by the preferred embodiment lies in recognizing the type of error, in order to give the second bold switch 112 a link 120 back to the first bold switch 106 in a form that provides for correct HTML interpretation. However, there is no standard HTML representation for such a link. An alternative is to copy the desired structure from the complementary parent node.

[0036] The preferred embodiment addresses these issues by reconstructing the tree structure of the HTML document, as the document is linearly read. Specifically, in such a reconstruction, each tag in a node does something to the tree, for example to start a node or end a node. Each node is created as being a child of the previous node. Errors occur when nesting within paragraphs is incomplete. A solution is that, as one traverses through the tree, to create a new node and to remember what has been traversed so that one can then trace back through the tree to correct the remaining nodes. As a consequence of such an arrangement, as represented in FIG. 1, the erroneous HTML may be corrected by creating an intuitive link 120 from the second bold switch 112 back to the first bold switch 106.

[0037] A specific example of such a solution is shown in FIGS. 2A to 2F in relation to the erroneous code of Code C depicted above. The example is also described with reference to the method 400 shown in the flow chart of FIGS. 4A to 4D.

[0038]FIG. 2A shows the inception of the tree structure corresponding to step 402 of FIG. 4A where a minimal tree is formed comprising a root node 200 identified by the tag “body”. Associated with the root node 200 at step 402 is a corresponding insertion point 202 indicating a location at which a child node is to depend. The creation of the tree structure arises from a process such as an HTML parser which provides a stream of new elements. A new element in this regard is a new node which may be added to the tree corresponding to a tag from the input stream. These may include opening tags or ending tags, noting that text functions as an opening tag for the purposes of the described method.

[0039] The next step 404 in the method 400 is the fetching of a new, or next, element (NE), which is followed by step 406 where a recreate list (RL) is emptied in anticipation of an insertion process for the element into the tree. Step 408 follows which performs a test to determine if an “end tag” is being handled. This is determined directly from the HTML code. Code C here includes an opening tag <P> and step 408 returns “No”. Control then passes to step 412 of FIG. 4C. Step 412 commences a process which determines an insertion rule that matches the opening tag with the insertion point (IP) 202 of the tree. The process includes step 414 which assesses whether the insertion point 202 is suitable for a new element. Ink Code C, the new element is a paragraph which is determined as suitable for appending to the body node 200 and hence step 414 is satisfied. Step 416 follows and the paragraph 204 is appended to the tree as a child node at the insertion point 202. This is seen in FIG. 2B. Step 418 (FIG. 4C) follows to determine if the new element just inserted (ie. the paragraph 204) is suitable for use as in insertion point. If so, as in the case of the paragraph 204, step 420 is implemented where the insertion point 206 is set to refer to the new element (ie. the paragraph 204). If the new element is not suitable as an insertion point, step 420 is bypassed and control passes to step 428 of FIG. 4B. Step 428 creates link-back nodes from references in the recreate list and below the insertion point 206 and makes the last new node the current insertion point Control then returns t step 404 to get the next element.

[0040]FIG. 2C follows in a similar fashion whereby the next node 208 corresponding to the bold switch is appended to the first child node 204, and a new insertion point 210 created.

[0041]FIG. 2D illustrates the inclusion of text 212 of the first paragraph and depending from the insertion point 210. It is noted in this regard that in FIG. 2D, the insertion point 210 remains depending from the bold node 208 because, under the HTML standard, text cannot be conceived as a container of other tags (ie. additional nodes in the tree). In this regard, the text is the specific content of the document as opposed to something that marks-up the manner in which the content is presented. In this regard, the method steps of FIG. 4A and 4C described above are followed again until step 418 is reached, returning a “No”. Step 428 then follows which, since the paragraph is unsuitable as an insertion point, retains the bold node 208 as the current insertion point 210.

[0042] Control again returns to steps 404 and 406 and a further parsing of the Code C reveals an opening tag for the second paragraph. If the second paragraph of Code C were to be added at the current insertion point 210, such would violate the HTML rule that paragraphs cannot be nested within each other. According to the preferred embodiment, the insertion point 210 is retraced back along the tree to a point where the new paragraph can be appended. Specifically, in tracing back, which occurs within a loop between steps 460 (FIG. 4D) and 412 (FIG. 4C) it is noted that the bold node 208 is to be recreated, resulting from the operation of step 448 and 450 (to be described). The insertion point then passes to the paragraph 204. Traversal then returns to the root node 200 where it is determined that a new paragraph may be appended thereto (ie. steps 412 and 414). The new instruction for the creation of the second paragraph is shown in FIG. 2E, with the creation of paragraph 214 appended to the root node 200 (ie. step 416). A new insertion point 216 is created (ie. steps 419 and 420).

[0043] The various corrections relating to the described examples may be summarised in tabular form below, where the bracketed numerals represent steps in the method 400 at which the relevant determination is made. TABLE 1 End Tag Rules New Tag (ending tag) Body Bold Paragraph Insertion Body Discard (432) Discard (432) Discard (432) Point Bold Discard (432) Yes (424) Preserve Parent (434) Paragraph Discard (432) Discard (432) Yes (424)

[0044] TABLE 2 New Tag Rules New Tag (NE) Body Bold Paragraph Text Insertion Body Discard (421) Parent (442) Yes (414) Parent Point (442) Bold Yes Yes (414) No, Yes (422) & (448) but recreate (414) (422 & 448) Para- Yes Yes (414) No Yes graph (422) & (448) (422 & 448) (414 

[0045] Further rules may be developed which seek to relate each individual HTML tag with each other HTML tag, the rules acting to perform the correction function desired for the particular application. Where appropriate or desired, certain rules may be classified into groups and any exceptions noted.

[0046] This process occurs via steps 408, 412 and 414, the latter returning a “No”, since one paragraph cannot be a child of another. Step 421 (FIG. 4C) is then performed to determine if the new element may be discarded. This may occur in a few instances of text and related tags in bad spots in tables and controls. For example, tags such as BOLD and ITALIC only have relevance to text content and not to other content, such as tables. In the present case, the new element will not be discarded and step 422 follows where the parent node of the current node, identified by the insertion point is tested. If the parent is valid, as in the present case, the test of step 448 is then performed. In the present case the rule tables above state that the parent may be preserved. Step 450 then adds a reference to the insertion point 210 to the recreate list. Step 452 assesses whether the top of the tree has been reached. In the present example, this is not the case and step 454 which follows makes a new insertion point to the parent of the node (ie. the paragraph 204 of FIG. 2D) These steps are then repeated until the insertion point is retraced back to the root note, in this case the body node 200. When this occurs, step 414 can then determine that the insertion point is suitable for the new element and, as before, the second paragraph 214 is appended to the body node and the insertion point updated to 216, giving the configuration of FIG. 2E.

[0047] The next step in the processing is to recreate each of the elements that were passed in the first branch of the tree prior to the new instruction being added. The result is seen in FIG. 2F where, appended to the paragraph 214, is a bold element 218 corresponding to the bold element 208 having been traversed in the first branch of the tree. The insertion point is updated to the bold 222 at which text of the second paragraph 220 may be appended.

[0048] This process may be understood with reference again to the flowcharts, where further parsing of Code C reveals the text content of the second paragraph as the next element. Steps 404, 408 and 412 are performed on further parsing of Code C, in this case again interpreting the text as an opening tag. Steps 414, 416 and 418 follow as before. With the insertion point stored in the recreation list remaining appended to the bold 210 (from step 450 discussed above), step 420 is then performed followed by step 428 where a link-back node 218 is then established from the recreate list and depending from the existing insertion point 216. The node 218 forms a link 224 seen in FIG. 2F. Because the link points to the bold node 208, the link-back node 218 thus operates as a bold node. This provides for the insertion point to then be updated to be the point 222 associated with the link-back node 218 according to step 428.

[0049] Further parsing of Code C reveals the end tag </BODY>, and hence step 408 is followed by step 424. In this case, the end tag relates to BODY and does not end the insertion point attached to the second paragraph. Hence step 430 follows to determine an ending rule to match the tag and the insertion point. Step 432 proposes a rule which ignores the end tag. Table nodes often absorb end tags this way aid this limits the scope of an end tag, this being performed for historical and/or arbitrary reasons arising from the somewhat haphazard development of HTML. In the present case, such is not appropriate and step 434 follows where the parent node may be preserved. This can be performed and step 436 adds a reference to the insertion point. Step 438 which causes the insertion point to be retraced back to the body node 200 thereby, when the top of the tree is reached, step 440 is performed resulting in the discarding of the end tag. This means in this case that content after the end body tag can still be added, in the case of a deliberate error putting content after an end of body tag. In the preferred embodiment, it is important that the extra node link back to the original node, rather than simply being another node of the same type, for example copied from the original node. The reason for this is that it is possible for languages to associate information with nodes according to the structure of the HTML document, this being a more elegant and computationally flexible solution than the “brute-force” method of copying sections of code. In this regard, Code E below incorporates a component of CSS2 code that sets the colour of a bold element that is the child of a paragraph that is the first child of its parent. Code E <HEAD> <STYLE>          } P:first-child B{color:red}    } CSS2 code </STYLE>          } <BODY> <P><B>The first paragraph. <P>The second paragraph. </BODY>

[0050] The purpose of Code E will be appreciated is to colour the paragraphs with the colour red. The commonly expected behaviour of such code, given that it is represented by incorrect HTML, is that the second paragraph would thus also be coloured red. If the structural correction of the preferred embodiment had been the equivalent of putting a fully independent bold element in the second paragraph, then that second bold element would not have matched the selector for the rule which applied the colour of red. The preferred method for implementing such presentation is to work forward through the original HTML source document constructing the expression tree as the traversal proceeds. A notion of the current insertion point into the tree is maintained as the tree is formed. The input of the tree is broken into two types of instructions, firstly those that create a new node (either because of the new element tag or text content, or secondly to end a node, because of the existence of closing tags. When a new element is attempted to be added to be added to the tree, the new element is tested to determine if it is of a type that is permitted to be nested at the current insertion point. If the new element is acceptable, then the new element is added to the tree and a new insertion point created unless the element is of a type that must always be a leaf node in the tree. If it is not acceptable to add the new element at the current insertion point, the preferred embodiment works its way back through the parent nodes noting those parent nodes which are required to be recreated as link back nodes in the new node. If an acceptable parent node is identified, the new element node is created and the link back nodes are added to the new element node. If an ending tag is encountered, the tree is traversed back through the ancestors from the insertion point noting in order those nodes need to be linked back. This proceeds until an element is identified that requires termination. The parent of the terminated element then made to be the new insertion point to which the new link back nodes are added. As each link back node is created, that node becomes an insertion point in its own right. Accordingly, if there are any multiple link back nodes, each would be created as a child of the previous link back in terms.

[0051] Returning to the CSS2 code indicated in Code E above, and the method steps depicted in FIGS. 2A to 2F, two alternatives arise for the appropriate processing of the CSS2 information. The first alternative is to do a first pass on the tree to obtain all CSS2 information, being those which require the fetching of additional documents to get the CSS2 information. This information is retained in memory so that each time a node is placed, a check can be determined as to whether the CSS information applies and if so, it is then applied to the node. Such an alternative however will not work for dynamic HTML. A solution to this is a further alternative where, as in the step depicted by FIG. 2F, a vector is formed which links back between the second bold node 218 to the original bold node 208 from which it was created so that the CSS information can be copied from the original node but link being shown in FIG. 2F as the link 224.

[0052] The restructuring method of FIGS. 2A to 2F and generally described herein are preferably practiced using a conventional general-purpose computer system 300, such as that shown in FIG. 3 wherein the restructuring processes are implemented as software, such as an application program executing within the computer system 300. In particular, the steps of the restructuring method are effected by instructions in the software that are carried out by the computer. The software may be divided into two separate parts; one part for carrying out the restructuring methods; and another part to manage the user interface between the latter and the user. The software may be stored in a computer readable medium, including the storage devices described below, for example. The software is loaded into the computer from the computer readable medium, and then executed by the computer. A computer readable medium having such software or computer program recorded on it is a computer program product. The use of the computer program product in the computer preferably effects an advantageous apparatus for restructuring HTML documents in accordance with the embodiments of the invention.

[0053] The computer system 300 comprises a computer module 301, input devices such as a keyboard 302 and mouse 303, output devices including a printer 315 and a display device 314. A Modulator-Demodulator (Modem) transceiver device 316 is used by the computer module 301 for communicating to and from a communications network 320, for example connectable via a telephone line 321 or other functional medium. The modern 316 can be used to obtain access to the Internet, and other network systems, such as a Local Area Network (LAN) or a Wide Area Network (WAN).

[0054] The computer module 301 typically includes at least one processor unit 305, a memory unit 306, for example formed from semiconductor random access memory (RAM) and read only memory (ROM), input/output (I/O) interfaces including a video interface 307, and an I/O interface 313 for the keyboard 302 and mouse 303 and optionally a joystick (not illustrated), and an interface 308 for the modem 316. A storage device 309 is provided and typically includes a hard disk drive 310 and a floppy disk drive 311. A magnetic tape drive (not illustrated) may also be used. A CD-ROM drive 312 is typically provided as a non-volatile source of data. The components 305 to 313 of the computer module 301, typically communicate via an interconnected bus 304 and in a manner which results in a conventional mode of operation of the computer system 300 known to those in the relevant art. Examples of computers on which the embodiments can be practised include IBM-PC's and compatibles, Sun Sparcstations or alike computer systems evolved therefrom.

[0055] Typically, the application program of the preferred embodiment is resident on the hard disk drive 310 and road and controlled in its execution by the processor 305. Intermediate storage of the program and any data fetched from the network 320 may be accomplished using the semiconductor memory 306, possibly in concert with the hard disk drive 310. Reconstruction of the tree according to the preferred embodiment may be performed in the memory 306. In some instances, the application program may be supplied to the user encoded on a CD-ROM or floppy disk and read via the corresponding drive 312 or 311, or alternatively may be read by the user from the network 320 via the modem device 316. Still further, the software can also be loaded into the computer system 300 from other computer readable medium including magnetic tape, a ROM or integrated circuit, a magneto-optical disk, a radio or infra-red transmission channel between the computer module 301 and another device, a computer readable card such as a PCMCIA card, and the Internet and Intranets including e-mail transmissions and information recorded on Websites and the like. The foregoing is merely exemplary of relevant computer readable mediums. Other computer readable mediums may be practiced without departing from the scope and spirit of the invention.

[0056] The restructuring methods described above permit poorly formed HTML to be interpreted restructured into a syntax corresponding to the HTML standard. As a consequence, that restructured syntax may then be interpreted by a browsing application thereby enabling consistent reproduction according to the HTML standard.

[0057] Although examples described above in relation to the preferred embodiment relate to text, paragraphs, and bold operators, similarly issues can arise through the interpretation of other switches, content, and the like which prevail the HTML standards. This may also include the provisional of italicised text, incorporation of images and the presentation and images in tables and the like.

Industrial Applicability

[0058] It is apparent from the above that the embodiment(s) of the invention are applicable to the computer and data processing industries, and in particular to computer network browsing software applications where the application may be exposed to a wide variety of documents, each purporting to coincide with a particular standard, but not necessarily conforming to that standard.

[0059] The foregoing describes only one embodiment of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiment being illustrative and not restrictive. 

1. A method of restructuring an input HTML document to comply with strict HTML, said method comprising the steps of: (a) linearly traversing said input HTML document to create a hierarchical tree structure representation, said traversal maintaining a current insertion point for elements within said tree structure representation; (b) during said traversal, identifying those elements of said input HTML document that violate strict HTML and, for each said identified element: (b)(i) retracing said tree structure representation from said current insertion point to identify an further insertion point from which said identified element can depend, said retracing comprising noting each parent element of said identified element passed during said retracing; (b)(ii) at said further insertion point, creating new elements in said tree structure representation corresponding to those said parent elements passed during said retracing, said new elements being created in reverse chronological order to that encountered during said retracing; and (b)(iii) appending said identified element to a terminal one of said new elements; and (c) converting said tree structure representation into an output HTML document.
 2. A method according to claim 1 , wherein step (b)(iii) comprises creating a link from said appended identified element to a first said parent element encountered during said retracting.
 3. A method according to claim 2 wherein said link comprises a vector.
 4. A method according to claim 1 wherein step (b)(iii) comprises copying a syntax of a first said parent element encountered during said retracting to said appended identified element.
 5. A method according to claim 1 , wherein one or more of said elements comprises information associated therewith, said method comprising the further steps, before step (a) of: performing an initial pass of said input HTML document to identify said elements having said associated information, and maintaining a record of each such element and the corresponding associated information whereby each time said element is placed in said tree structure representation, the corresponding associated information is associated therewith.
 6. A method according to claim 1 comprising the further step of: (d) reproducing said output HTML document.
 7. A method according to claim 6 wherein said output HTML document is reproduced using a video display.
 8. A method according to claim 6 wherein said output HTML document is reproduced using a printer.
 9. Apparatus for restructuring an input HTML document to comply with strict HTML, said apparatus comprising: means for linearly traversing said input HTML document to create a hierarchical tree structure representation, said traversal maintaining a current insertion point for elements within said tree structure representation; means for identifying, during said traversal, an element of said input HTML document that violates strict HTML; means for retracing said tree structure representation from said current insertion point to identify an further insertion point from which said identified element can depend, said retracing comprising noting each parent element of said identified element passed during said retracing; means for creating, at said further insertion point, at leats one new element in said tree structure representation corresponding to those said parent elements passed during said retracing, said new elements being created in reverse chronological order to that encountered during said retracing; and means for appending said identified element to a terminal one of said new elements; and means for converting said tree structure representation into an output HTML document.
 10. Apparatus according to claim 9 , wherein said means for appending creates a link from said appended identified element to a first said parent element encountered during said retracting.
 11. Apparatus according to clam 10 wherein said link comprises a vector.
 12. Apparatus according to claim 9 wherein said means for appending copies a syntax of a first said parent element encountered during said retracting to said appended identified element.
 13. Apparatus according to claim 9 , wherein one or more of said elements comprises information associated therewith, and said apparatus Finer comprises: means for performing an initial pass of said input HTML document to identify said elements having said associated information, and for maintaining a record of each such element and the corresponding associated information whereby each time said element is placed in said tree structure representation, the corresponding associated information is associated therewith.
 14. Apparatus according to claim 9 further comprising: means for reproducing said output HTML document.
 15. Apparatus according to claim 14 wherein said means for reproducing comprises a video display.
 16. Apparatus according to claim 14 wherein said means for reproducing comprises a printer.
 17. A computer readable medium, having a program recorded thereon, where the program is configured to make a computer execute a procedure to restructure an input HTML document to comply with strict HTML, said program comprising: code for linearly traversing said input HTML document to create a hierarchical tree structure representation, said traversal maintaining a current insertion point for elements within said tree structure representation; code for, during said traversal, identifying an element of said input HTML document that violate strict HTML; code for retracing said tree structure representation from said current insertion point to identify an further insertion point from which said identified element can depend, said retracing comprising noting each parent element of said identified element passed during said retracing; code for creating new elements in said tree structure representation at said further insertion point, said new elements corresponding to those said parent elements passed during said retracing, said new elements being created in reverse chronological order to that encountered during said retracing; and code for appending said identified element to a terminal one of said new elements; and code for converting said tree structure representation into an output HTML document.
 18. A computer readable medium according to claim 17 , wherein code for appending comprises code for creating a link from said appended identified element to a first said parent element encountered during said retracting.
 19. A computer readable medium according to claim 18 wherein said link comprises a vector.
 20. A computer readable medium according to claim 17 wherein said code for appending comprises code for copying a syntax of a first said parent element encountered during said retracting to said appended identified element.
 21. A computer readable medium according to claim 17 , wherein one or more of said elements comprises information associated therewith, and said program further comprises: code for performing an initial pass of said input HTML document to identify said elements having said associated information, and for maintaining a record of each such element and the corresponding associated information whereby each time said element is placed in said tree structure representation, the corresponding associated information is associated therewith.
 22. A computer readable medium according to claim 17 , said program further comprising: code for reproducing said output HTML document.
 23. A computer readable medium according to claim 22 wherein said output HTML document is reproduced using a video display.
 24. A computer readable medium according to claim 22 wherein said output HTML document is reproduced using a printer. 